Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 899-tree-1
name: 1499
tree-preservation-order: undefined
899-tpo-1
uprn
address-text
point: POINT (-0.970426 50.865001)
geometry: MULTIPOLYGON (((-0.970383 50.864997,-0.970385 50.865005,-0.970391 50.865013,-0.970400 50.865019,-0.970412 50.865023,-0.970425 50.865024,-0.970439 50.865023,-0.970451 50.865019,-0.970460 50.865013,-0.970466 50.865006,-0.970469 50.864998,-0.970467 50.864989,-0.970461 50.864982,-0.970451 50.864976,-0.970440 50.864972,-0.970427 50.864970,-0.970413 50.864971,-0.970401 50.864975,-0.970392 50.864981,-0.970386 50.864988,-0.970383 50.864997)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL